BBS Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ BBS Toolkit / BBS Toolkit.iso / remote / mc_cbv11.zip / MC_CBV.DOC < prev next >

Wrap

Text File | 1993-03-26 | 23KB | 445 lines

=============================================================================== Program : MC_CBV Version : 1.10 Contact : Rod Hancock Date : Mar 26, 1993 Voice : (416) 404-2756 FidoNet : 1:229/418 =============================================================================== Mc_Cbv Automated Callback Verifier for RemoteAccess Copyright 1992,1993 Motor City Software All Rights Reserved ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Introduction ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ This is Motor City Software's CallBack Verification System for RemoteAccess. Shareware Version ----------------- - Works with RemoteAccess V1.1x and V2.00. - Detects and Gives Up TimeSlices with DESQView AND OS/2 - Checks Users Phone Numbers to make sure they are in the correct format if you are using USA Style numbers. - Duplicate Phone Number Checking by Numbers Already Called or by Numbers in Users.BBS - Post Welcome Message to newly verified users - Messages are fully configurable with Message Templates - Excellent Call Collision Handling - Allows Multiple LOCAL Area Codes - Sysop Configurable for Allowing LD Callbacks, including Setting Specific Hours for Long Distance calls, AND Specific Area Codes and Exchanges! - The Sysop can define much of the displayed text. - One of the easiest doors you ever set up! Reads all its defaults from your RemoteAccess configuration files! - Originally written for the RA Beta Team - Secure Password Checking using CRC32 with RemoteAccess 2.00 - If the User has less than X Minutes remaining when they enter the CallBack Door, they will have their time reset to X minutes in order to allow them to complete the CallBack Process. X is configurable by the Sysop. - The Sysop may abort the callback by hitting ESCAPE, or abort the current call attempt with the SPACE bar. - Fully Multi-Node Aware - The Following Sysop Keys are available in the door for the Sysop : Alt-C Chat With User Alt-J Jump To Dos Alt-R Return To BBS UpArrow Add 1 Minutes Time DownArrow Deduct 1 Minutes Time Registered Version ------------------ - Post Messages To Sysop based on CallBack Completion Results - Set Validated Users Subscription Expiry Date - Set Validated Users User Group Number - Save verified phone numbers to the Users.Bbs (Choice of fields to save in) - Allow McCbv to build its own LOCAL dialing control file! YES, it will automatically verify and add local numbers to its control file as it finds them. This feature alone can save you HOURS of searching and typing! ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Licensing Information ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Motor City doors are commercial programs marketed under the "User Supported" or "Shareware" concept. You are allowed to install this program on Your system and evaluate it before deciding whether to purchase a license to continue using it. This program is not public domain or freeware. If you use this program for more than 30 days after successful installation, you are legally required to register it or remove all working copies from your system The User Supported or Shareware concept works only if you and your fellow sysops support it. If you find this program useful, you can register it for only $15.00 in U.S. funds. This will help offset the development costs, and encourage us to write other programs that might be useful to you. After all, no one likes to work for nothing! A Registration Form is included in the distribution archive. Mc_Cbv is Copyrighted 1992,1993 by Motor City Software, ALL RIGHTS RESERVED. You may copy this program and documentation for backup purposes. You also may copy and share UNMODIFIED copies of the original program archive. The copyright notice must remain attached to all copies. You may not sell Motor City Software products for a fee, or distribute them along with other products without written permission of Motor City Software, nor may you modify or remove the Copyright Notice from the program or the documentation. BBS operators who charge for access to their systems are exempt from this provision as long as no additional payment is required for access to Motor City Software products beyond basic file access. All Motor City Software products are extensively tested before being publicly released, but as with any software, bugs may still occur. Motor City Software products are provided as is, and neither Motor City Software nor any BBS operator distributing this software is responsible for any damage incurred during the operation of the program. You are advised to test all Motor City Software products thoroughly on a backup copy of your BBS before putting them online. Comments, suggestions and bug reports are welcome. If you have any, you may call one of the Motor City Software Support Systems listed in SUPPORT.DOC and leave a message to the Sysop. If you're reporting a bug, please give as much detail as possible describing the problem you are having, your system configuration, and if you would be willing to test possible corrections to the problem. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Upgrading From Previous Version ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ You will be required to delete your MC_CBV.CFG (If you don't, CBVSetup will!) READ this whole document as there are many changes, including NEW FORMATS for the MC_CBV.LOC and MC_CBV.LD files. The /NOAC commandline switch is no longer used, as Area Code stripping is now done using the MC_CBV.LD control file. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Setup ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Setting Up ---------- Run CBVSetup to configure the CallBack Verifier. Online help is available by hitting the F1 Key on any field. CBVSetup should be fully self explanatory if you read the help screens. Running Mc_Cbv.EXE - The Door itself ------------------------------------ Usage: Mc_Cbv /N2 /N Defines the node number using CBV. You may use /N*N on the optional data line in the RA Menu option. Example: D:\BBS\CBV\Mc_Cbv.EXE /N*N If No Command Line Parameters are used, then it defaults to NODE 1. Place Mc_Cbv.EXE in its own directory, and call the Mc_Cbv.EXE from your Top Menu as a type 7. It will look for the EXITINFO.BBS and DORINFO1.DEF in the CURRENT Directory. It will look for its own files in the same directory which the EXE file resides in. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Optional Message Template Files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Mc_Cbv will Post Messages to the Sysop or User if certain Message Template Files exist AND you chose a valid Hudson Message Base in CBVSetup. These files are ASCII Text files created using any text editor. We have included samples in an archive called MESSAGES.ARJ In each of these files, you will notice that line 1 contains the SUBJECT of the message. The rest of the lines may contain whatever you like, and the following TextFile Control Codes are Valid. (As used in RemoteAccess) ^FA - Current Users Full Name ^FW - Users First Name ^FO - Current Users Security Level ^F4 - Date of Current Users FIRST Call to BBS ^F6 - Current Users Subscription Expiry Date ^FE - Current Users Voice Phone Number ^FD - Current Users Data Phone Number ^F3 - Current Users Handle ^FB - Current Users Location ^F5 - Date Of Birth ^FP - Number of times the user has called your bbs ^FH - Users A Flags (8 Characters --XX-X-- ) ^FI - Users B Flags (8 Characters --XX-X-- ) ^FJ - Users C Flags (8 Characters --XX-X-- ) ^FK - Users D Flags (8 Characters --XX-X-- ) ^KA - Total Calls To Your BBS ^KR - Baud Rate ^KW - Two digit Node Number The following Templates have been included, and if they exist, and a valid Hudson Message Base has been chosen, will cause a message to be written. Feel free to modify these as you see fit. NONEED.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE and a user has a high enough security level to exempt them from using CBV, this message will be posted to alert you. NOTUSED.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE and the user for whatever reason does NOT use the CBV, then this will alert you. Once the template has been posted, a one line Reason is added to the message, explaining where the user Quit. VERIFIED.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE then this message will be posted to you when the user has completed the callback process. LDUPDATE.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE and you update LD callers without calling them back, this message will be posted to you. IEMSI.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE and you automatically update IEMSI users, then this message will be posted to you. FAILPW.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE and the user reconnects, but gets the password wrong, then this message will be posted to you. WELCOME.MSG - If this template exists in the same directory as Mc_Cbv.EXE then it will be posted to the USER when they are verified. This will include IEMSI and LD users if you update them without doing the callback. This can be used to give them more information about joining your BBS, or anything you desire. This message will be posted TO the User, From the Sysop as defined in Dorinfo1.Def NOTE: If you are NOT registered, then the ONLY Message that you may post is WELCOME.MSG to the user. A reminder is written to the end of this message stating that this is an Unregistered Evaluation Copy, and requires registration after evaluating it. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Optional Information text files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Mc_Cbv allows up to 7 text files to be used to describe the door for the users. If the file isn't present then Mc_Cbv will use default text. These files should be located in the same directory as Mc_Cbv.EXE Samples of these files are included in the archive CBV_TEXT.ARJ Brief descriptions are as follows: The files support the RA Text File Control Codes for UserName, Phone Numbers etc. ADDPHONE.TXT - Displayed to user before showing ASKPHONE.TXT ASKPHONE.TXT - Message to the User to see if the phone number looks right before before calling. EXPLAIN.TXT - If the user did not understand how to use the CBV, then this is where you may try to explain it one last time. If they still do not understand, then the door will exit and you will have to verify them another way, or they may try again. GETNUM.TXT - If you allow the user to enter another phone number to be called at, then this is displayed just prior to prompting for a phone number. If you are using NON-USA format numbers, you can use this to show the user the way YOU WANT the number entered. LOCHANG.TXT - Tells the User why the door is hanging up on them after a successful local callback. LDHANG.TXT - Tells the User why the door is hanging up on them after a successful long distance callback. NO_LD.TXT - Shown to Long Distance users if you don't allow LD calls. NOTTIME.TXT - Shown to Long Distance Users who you only call between certain hours. You may use this to show what Days and Times Long Distance Validation IS allowed for that users number. If you do not create this file, then a nice screen will inform the user of the times they may be validated. PRECALL.TXT - Shown just prior to dialing the users number and explains how to make their modem answer when they are called. TELSYSOP.TXT - Message to user if they say the number the door will call them at doesn't look right. UINFO.ANS - This is the User Information Screen. This one allows you to create an ANS and an ASC version and is displayed right after the Registration Info on the Screen. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Data text files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Samples are provided in the archive EXAMPLES.ARJ NOTE: Once you have created the MC_CBV.LOC and MC_CBV.LD files, I recommend you Scan them in CBVSetup. This option will scan these files and alert you of any INVALID lines in these files. This is useful if McCbv tells you that a call is NOT local, when you think that it has been defined properly within the MC_CBV.LOC file. This option is available on the EXIT Menu in CBVSetup. Data Text files: (* - means it's required) * Mc_Cbv.LOC - This file is used by McCbv to tell what phone numbers will be LOCAL Calls. This is much like FrontDoor, where it matches the users number against the first number, replacing the matching numbers with the dial string. Any line may be commented out by simply putting a semi-colon (;) in column 1. The first number MUST begin at column 1 in the file, and the string to dial MUST start at column 25 123456789012345678901234567890 416-404- 404- ;416-579- 579- 804-485- 485- 803-288- 803-288- ;This is a comment Field because it starts with ; in Column 1 In this case (416)404-2756 would be dialed as 404-2756 (416)579-XXXX would NOT be found as it is commented out. (804)485-2995 would be dialed as 485-2995 (803)288-2845 would be dialed as 803-288-2845 SPACES must be used to seperate the numbers, NOT Tabs! This should make it possible to use Mc_Cbv almost anywhere in the world, all you do is define enough of the phone number to allow McCbv to decide the number is local, and tell it how to dial it. This makes it easy to support more than one Local Area Code. > If you are REGISTERED you may use the following feature: > If you are using North American Format numbers and you enable > 'Attempt Unkown Local Calls' to Y, and a user enters a phone > number which matches an AREA CODE from your Mc_Cbv.Loc file, > then it will ask the user if this is a Long Distance number. > If the user says it is a Local call, then Mc_Cbv will strip > the area code, and attempt to dial it Without using a long > Distance Prefix, or area code. If it reconnects with the user > then obviously it IS a local call, and the proper entry will > be made to the Mc_Cbv.Loc file. If it was, in fact, Long > distance, you will simply get a recording from Bell, and no > charges will be incurred ( I ASSUME NO RESPONSIBILITY for > anything arising from using this feature. It DOES work here, > I simply hear the recording and the call will fail) > > The BARE MINIMUM Mc_Cbv.LOC file you will need to create to > get started is One Line for each Local Area Code. You MUST > enter one exchange from each area code. Eg. > > 416-404- 404- > 403-215- 215- > > From this point on, Mc_Cbv can build your Local Control File > for you!!! Mc_Cbv.LD - If you set YES to call Long Distance in CbvSetup, then it will call ANY long distance number. If you would like to limit long distance to certain Area Codes, or Exchanges within Area Codes then you may define them in Mc_Cbv.LD This file is Exactly like Mc_Cbv.LOC, and if it exists, ANY NUMBERS which match will be allowed. In CBVSetup, set Allow LD Calls to NO, and define the ones you WILL call in here. If you don't wish to call any Long Distance, or don't want to limit the numbers which can be called, then do not create this file. Numbers in this file OVERRIDE the setting in CBVSetup. Note: This file DOES OVERRIDE the settings in CbvSetup, but it WILL still honor the defined Long Distance Hours. IMPORTANT! If you wish to allow calls to TOLL numbers, that is numbers in your area code, which are NOT free calls, you MUST define that Area code in your .LD file. If you dial them as 1-AAA-XXX-XXXX then this is not needed, but if you dial them as 1-XXX-XXXX then define your area code as follows: Assume 416 is your local area code. 123456789012345678901234567890 416- 1- Mc_Cbv.LOG - Log of the doors activity. Made by the door. Mc_Cbv.BAD - List of phone number NOT TO CALL (ie your local police station fire station, etc.) Mc_Cbv will automatically not call 411, 911, 900 numbers and 555-1212 (directory assistance). You have to make this file if you want to define other Bad Numbers. Mc_Cbv.OK - List of numbers the door has successfully called. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Still Having Problems? ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ It is important to us that you are able to install and run our software with a minimum amount of effort on your part. Although we have tried to make this software as easy to use as possible, we do know that occasionally someone will have a problem. In order to provide the quickest response, we have a voice support number available, and all problems are usually solved with one quick phone call. See info at the top of this file. This is the FASTEST way to resolve any problems, although netmail messages will be replied to within 24 hours. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Special Thanks To... ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ I would like to thank the following people for all their help and wisdom.... Bob R, Geoffrey Booher, Bruce Bodger, David Smart, Chuck Corvec, and all those who contacted me with problems and helped to test the fixes... Special thanks to Mark McKay, who wrote the original code which this door is based on, and Peter Kling, and Jeff Wilson who each helped out as well. And, of course, Andrew Milner, for such a fantastic Bulletin Board System! The biggest thanks of all go to those who have already registered this program, setting a record here at Motor City Software for the number of registrations received within the shortest time of a first release!!! Rod Hancock Motor City Software <end of document>